Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

get involved #11

Merged
merged 2 commits into from
Aug 21, 2024
Merged

get involved #11

merged 2 commits into from
Aug 21, 2024

Conversation

oduameh
Copy link
Owner

@oduameh oduameh commented Jul 22, 2024

  • CHANGELOG updated or not needed
  • Documentation updated or not needed
  • Haddocks updated or not needed
  • No new TODOs introduced or explained herafter

@github-actions GitHub Actions

This comment was marked as off-topic.

Sign in to view
@github-actions GitHub Actions

This comment was marked as off-topic.

Sign in to view
@github-actions GitHub Actions
Copy link

Transaction costs

Sizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using arbitrary values and results are not fully deterministic and comparable to previous runs.

Metadata
Generated at 2024-07-22 11:30:40.294686938 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial e6685648e63ab510b49d2ce632c570d2ef53f44f3cbdf82ed553906c 4081
νCommit fce3b967fb72f4a3be8dfa30defe413258ff453e5d32d6752d83f9cf 2060
νHead 10a116037de398d6b0721152336d602f0ea653eb3dfe540d5da63fe4 9367
μHead 4f93fdfeda690e005d3f5a180208edd3f65ddd0892466ad7f4dd678b* 4236
  • The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per head.

Init transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 4815 5.79 2.29 0.43
2 5016 6.99 2.76 0.45
3 5219 8.69 3.44 0.47
5 5623 11.17 4.41 0.52
10 6627 18.11 7.16 0.64
58 16278 84.28 33.34 1.79

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 559 9.25 3.68 0.28
2 742 11.94 4.93 0.31
3 934 14.70 6.20 0.35
5 1313 20.44 8.83 0.44
10 2240 36.05 15.86 0.65
26 5247 98.14 42.75 1.48

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 56 543 14.13 5.69 0.33
2 113 654 22.50 9.15 0.43
3 170 768 32.28 13.25 0.54
4 228 874 44.85 18.48 0.68
5 281 984 57.69 23.92 0.83
6 337 1095 70.00 29.32 0.98
7 394 1205 85.38 35.93 1.15

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 560 7.82 3.75 0.27
2 730 8.74 5.57 0.29
3 891 9.40 6.64 0.31
5 1138 10.89 8.77 0.35
10 2014 15.71 15.37 0.48
50 7863 48.68 61.76 1.33

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 647 8.40 4.67 0.28
2 773 9.08 5.71 0.30
3 950 10.15 7.09 0.33
5 1252 11.94 9.54 0.37
10 2187 17.09 16.34 0.50
50 7771 48.37 61.21 1.32

Abort transaction costs

There is some variation due to the random mixture of initial and already committed outputs.

Parties Tx size % max Mem % max CPU Min fee ₳
1 4715 16.43 7.18 0.54
2 4765 25.97 11.34 0.65
3 4950 39.33 17.39 0.81
4 5173 57.49 25.55 1.03
5 5068 66.28 29.13 1.12
6 5366 90.59 40.12 1.41

FanOut transaction costs

Involves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.

Parties UTxO UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
5 0 0 4651 7.43 3.12 0.44
5 1 57 4685 8.94 3.99 0.46
5 5 284 4820 13.22 6.71 0.52
5 10 571 4991 18.61 10.14 0.59
5 20 1137 5328 29.59 17.07 0.75
5 30 1709 5671 41.57 24.43 0.91
5 40 2276 6008 52.76 31.46 1.07
5 50 2841 6344 63.17 38.15 1.21
5 82 4665 7432 99.43 60.85 1.72

End-to-end benchmark results

This page is intended to collect the latest end-to-end benchmark results produced by Hydra's continuous integration (CI) system from the latest master code.

Please note that these results are approximate as they are currently produced from limited cloud VMs and not controlled hardware. Rather than focusing on the absolute results, the emphasis should be on relative results, such as how the timings for a scenario evolve as the code changes.

Generated at 2024-07-22 11:04:30.130535933 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.750082112
P99 11.572365909999997ms
P95 6.606665899999996ms
P50 4.3824024999999995ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.303074234
P99 104.19819138000005ms
P95 30.407522149999995ms
P50 19.9754295ms
Number of Invalid txs 0

@github-actions GitHub Actions
Copy link

Transaction costs

Sizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using arbitrary values and results are not fully deterministic and comparable to previous runs.

Metadata
Generated at 2024-07-22 12:15:05.41295758 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial e6685648e63ab510b49d2ce632c570d2ef53f44f3cbdf82ed553906c 4081
νCommit fce3b967fb72f4a3be8dfa30defe413258ff453e5d32d6752d83f9cf 2060
νHead 10a116037de398d6b0721152336d602f0ea653eb3dfe540d5da63fe4 9367
μHead 4f93fdfeda690e005d3f5a180208edd3f65ddd0892466ad7f4dd678b* 4236
  • The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per head.

Init transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 4821 5.98 2.37 0.43
2 5016 6.99 2.76 0.45
3 5220 8.56 3.39 0.47
5 5626 11.41 4.51 0.52
10 6625 18.02 7.12 0.64
58 16282 84.28 33.34 1.79

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 556 9.25 3.68 0.28
2 749 11.94 4.93 0.32
3 937 14.70 6.20 0.35
5 1307 20.44 8.83 0.44
10 2242 36.05 15.86 0.65
26 5242 98.14 42.75 1.48

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 544 14.18 5.70 0.33
2 113 654 22.20 9.04 0.42
3 170 764 32.60 13.37 0.54
4 225 874 43.66 18.04 0.67
5 283 984 58.49 24.24 0.84
6 339 1095 70.26 29.40 0.98
7 393 1205 85.48 35.97 1.15

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 591 8.04 4.51 0.27
2 727 8.65 5.54 0.29
3 887 9.48 6.67 0.31
5 1329 12.54 10.13 0.38
10 2063 16.40 15.76 0.49
50 7905 47.62 61.67 1.33

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 623 8.31 4.61 0.28
2 757 9.12 5.72 0.30
3 1036 10.70 7.52 0.34
5 1224 11.68 9.27 0.37
10 1937 15.39 14.90 0.47
50 7821 49.02 61.65 1.33

Abort transaction costs

There is some variation due to the random mixture of initial and already committed outputs.

Parties Tx size % max Mem % max CPU Min fee ₳
1 4684 16.52 7.20 0.54
2 4853 27.91 12.33 0.68
3 4962 41.11 18.19 0.83
4 5204 57.89 25.74 1.03
5 5190 68.95 30.48 1.16
6 5423 97.24 43.23 1.49

FanOut transaction costs

Involves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.

Parties UTxO UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
5 0 0 4650 7.43 3.12 0.44
5 1 57 4684 8.94 3.99 0.46
5 5 285 4820 13.22 6.71 0.52
5 10 570 4991 18.80 10.22 0.60
5 20 1139 5330 29.59 17.07 0.75
5 30 1709 5671 41.17 24.26 0.91
5 40 2278 6010 52.36 31.29 1.06
5 50 2847 6349 63.56 38.32 1.22
5 82 4664 7430 99.82 61.02 1.72

End-to-end benchmark results

This page is intended to collect the latest end-to-end benchmark results produced by Hydra's continuous integration (CI) system from the latest master code.

Please note that these results are approximate as they are currently produced from limited cloud VMs and not controlled hardware. Rather than focusing on the absolute results, the emphasis should be on relative results, such as how the timings for a scenario evolve as the code changes.

Generated at 2024-07-22 12:17:24.117563966 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.165251869
P99 9.358075399999906ms
P95 4.722360599999998ms
P50 3.6443835ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 20.871551824
P99 57.63295870000002ms
P95 29.547918449999997ms
P50 18.6631535ms
Number of Invalid txs 0

@github-actions GitHub Actions
Copy link

Test Results

437 tests  ±0   425 ✅ ±0   15m 0s ⏱️ -23s
143 suites ±0    12 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit 4b06028. ± Comparison against base commit d6040f5.

@oduameh oduameh merged commit 3cc7027 into master Aug 21, 2024
21 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@olgahryniuk olgahryniuk olgahryniuk approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@oduameh @olgahryniuk